home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
lan
/
merc130.zip
/
README.NDS
< prev
next >
Wrap
Text File
|
1996-05-30
|
33KB
|
657 lines
Using Pegasus Mail and Mercury in NDS Mode under NetWare 4.1
------------------------------------------------------------------
Introduction
This document covers the operating theory of Pegasus Mail in the NetWare
4.1 environment using Novell's NDS user database structure. The target
audience for this file is system administrators and those who are charged
with maintaining the mail system. Because of the complexity of the
NetWare 4.1 environment, we strongly recommend that you take some time to
read this document thoroughly. We do, however, realise that many sites
would prefer to get straight into things, so if you wish, you can bypass
the theory and go straight to a step-by-step setup procedure by reading
the file QSETUP.TXT supplied in this archive.
Contents:
1: Summary
2: Overview and operating requirements
3: Contexts and operation
4: Addresses
5: Synonyms (alternative addressing formats)
6: Installing Pegasus Mail for Windows in NDS Mode
7: Installing Mercury in NDS Mode
7.1: Modifying MERCURY.INI for NDS use.
8: Allowing Local User Lookup
9: Extended Features
10: Security Considerations
11: POP3 server considerations
12: Troubleshooting
1: Summary
This document provides information on running NDS-aware versions of
Pegasus Mail for Windows and the Mercury MTS on NetWare 4.1 systems.
Because NetWare 4.1 does not have some of the features of NetWare 3.x
that made it possible to create a maintenance-free mail system, some
extra work is required to set it up for optimum use, so you should
take the time to familiarise yourself with this document thoroughly
before attempting the installation.
In brief, installing Pegasus Mail for Windows entails following these
steps:
* Install WPNNW4.DLL into the same directory as WINPMAIL.EXE
* Make sure current versions of the Novell API DLLs are installed
on your system
* Run the NDS-Aware version of PCONFIG to configure WinPMail for
each context on your server that needs its own configuration.
* Run the Pegasus Mail MAKEMBOX utility to create user mail
directories as required in each configured context.
* [Optional] Run the PMIGRATE utility to copy the mailbox contents
of any user who has previously run Pegasus Mail in Bindery Emulation
mode on your server to the new mailbox location.
* Install PMUSER.NLM, the mailbox maintenance utility, on your file
server.
* [Optional] Make a small change to NDS to allow local user lookup
(see section 7 in this file).
Installing the NDS-Aware version of Mercury on your file server is a
simpler process requiring these steps:
* If you have never installed Mercury before, run SETUP.EXE
-- or --
* Install MERCNDS.NLM and MERCNDSS.NLM in SYS:SYSTEM
* Add a couple of new sections to your MERCURY.INI file
* [Optional] Install MERCNDSP.NLM in SYS:SYSTEM for POP3 support.
Installing Pegasus Mail and Mercury in NDS mode is slightly more complex
than it is in Bindery Mode, but the ultimate aim is to produce a system
with little or no ongoing maintenance or management requirement at the
expense of a small amount of relatively simple extra initial setup and
configuration.
2: Overview and operating requirements
In NDS mode, Pegasus Mail no longer uses the old NetWare 3.x SYS:MAIL
directory structure to deliver and store mail: instead, it expects to
deliver mail to a directory called PMAIL in each user's home directory on
the file server. The MAKEMBOX utility creates the necessary directories
for existing users, while the PMUSER NLM creates them automatically for
each user that is created in future. The aim is to produce a system that
is as nearly maintenance-free as possible, and to isolate Pegasus Mail
from further disastrous changes in Novell system policy in future.
Clearly, though, there are a couple of specific requirements that must
be met in order to make this work:
* All mail users must have a writable home directory in which they
have full rights.
* PMUSER.NLM must be run on every file server containing a partition
where Pegasus Mail users could be created.
PMUSER.NLM uses one service connection and about 10KB of server RAM in
normal use, and introduces almost no load on your server when it is idle.
PMUSER.NLM is not required if you use the NDS-Aware version of Mercury
to handle all of your mail delivery, since Mercury can duplicate the
functionality of PMUSER. Running PMUSER, however, allows Pegasus Mail's
local delivery agent to function normally, just as it always has under
NetWare 3.x and earlier.
3: Contexts and operation
NDS provides a tree structure which can contain many organizational
units. Pegasus Mail's NDS-awareness supports the full idea of NDS,
allowing different configurations for specific organizational units
within your NDS tree. You can also create configurations that apply to a
particular subtree of the NDS hierarchy, or even to the whole NDS tree by
choosing where you place the configuration information.
To find its configuration information, Pegasus Mail starts in the user's
"Home context" - the organizational unit in the tree where the user was
created, and looks for a "Profile" object called "Pegasus Mail". If it
finds it, it parses the object's "Login script" attribute for its
configuration information. If it does not find the object, it changes up
one level in the NDS tree and repeats the search. The search continues
until either a configuration object is found, or else the root of the
tree is reached without finding a record. The NDS-aware version of
PCONFIG creates and maintains the "Pegasus Mail" profile object for you,
ensuring that all users have the rights necessary to be able to read its
login script. The Profile Object Pegasus Mail uses is, however, a
standard NDS data type, and can be easily manipulated using standard
Novell tools such as NWADMIN or NETADMIN, provided the user doing so has
sufficient rights.
Unlike running in NetWare 3.x mode, Pegasus Mail MUST find at least one
configuration record somewhere in the tree or it will refuse to run. The
context where Pegasus Mail finds its configuration record is known as the
"Configuration context" and is important for other reasons: Pegasus
Mail's control groups, such as GROUPMAIL, MAILUSERS and NOMAIL must all
be located in the configuration context in order to operate. Similarly, a
simple mail address, such as "Peter" is presumed to be relative to the
configuration context. This brings us to the next topic...
4: Addresses
Just as it does under NetWare 3.x, Pegasus Mail uses the native NetWare
user naming structure when running in NDS mode. So, you can enter
addresses like "Admin.pmail", or "CN=Admin.O=PMAIL" and Pegasus Mail will
accept these as normal addresses, routing the mail as required. You can
also use "relative addresses" - so if there is an organizational unit
called "Dev" in the configuration context and it contains a user called
"David", you can use "David.Dev" as an address as well.
Provided you install Pegasus Mail correctly in NDS mode, it can easily
act as a low-maintenance enterprise-wide mail system providing mail
services to all users throughout your NDS hierarchy.
5: Synonyms (alternative addressing formats)
Many sites have policies mandating that particular addressing formats
should be used in their outgoing Internet mail - for example, a site may
want its users' Internet addresses to consist of their initials and
surname, like this: D.L.Harris@pmail.gen.nz. Basic address changes like
this are beyond the scope of simple aliasing - they require the
co-operation of both the mail program (Pegasus Mail) to ensure that the
"from" field of the message is written properly in outgoing mail, and also
of the Mail Transport System (Mercury) to ensure that incoming mail using
the alternative address format is routed to the proper user. In the Pegasus
Mail and Mercury systems, an address of this kind, which is